EPrints 3.4.4

From EPrints Documentation
(Redirected from Files/EPrints 3.4.4)
Jump to: navigation, search

Release Notes

3.4 | 3.4.1 | 3.4.2 | 3.4.3 | 3.4.4 | 3.4.5 | 3.4.6


3.3 | 3.3.5 | 3.3.6 | 3.3.7 | 3.3.8 | 3.3.9 | 3.3.10 | 3.3.11 | 3.3.13 | 3.3.14 | 3.3.15 | 3.3.16


3.2.0 | 3.2.1 | 3.2.2 | 3.2.3 | 3.2.4 | 3.2.5 | 3.2.6 | 3.2.7 | 3.2.8 | 3.2.9


3.1.0

Release Notes

EPrints 3.4.4 is now available on files.eprints.org and GitHub.

  • Zero codename: Lemon Trifle Bora
  • Publications flavour codename: Amaretti Biscuit Haboob (1.4)

New Dependencies

For future facilitation of interchangeable JavaScript libraries, Prototype JavaScript currently used by EPrints has been moved to become an ingredient. Therefore, for those upgrading their repository the following line needs to be added to your flavour's inc file (e.g. /opt/eprints3/flavours/pub_lib/inc):

ingredients/prototypejs

Be sure to hard refresh (e.g. Ctrl+Shift+R) your web browser (after add this ingredient and reload your web server) to clear the JavaScript client-side cache.

Check earlier dependencies for EPrints 3.4.3 and before.

Changes Since 3.4.3

New Functionality

Security and Privacy Improvements

General Improvements

Bug Fixes

Known Issues

LDAP-based authentication for new users

If you use LDAP-based authentication to login users and your $c->{check_user_password} function includes code that creates new user accounts on-the-fly if they do not already is exists in EPrints, then users without a pre-existing user account will no longer be able to login. This is due to code implemented to allow user accounts to be locked if there were too many consecutive failed login attempts. This patch has been created to fix the issue by not requiring a user account to exist, which means a new user account can be created but there can be no restriction on how many times non-registered user can attempt to login as there is no user account that can be locked.

JavaScript and CSS caching

JavaScript and CSS in static/javascript/auto/ and static/style/auto/ directories can be updated without the /javascript/auto-VERSION.js and /style/auto-VERSION.css loaded in page template being updated unless the server-side cached versions in the archive's html/LANG/javascript/ and html/LANG/style/ directories being purged. This was due to an intended improvement adding incrementing parameter to the links in the page template to better expiry the client-side caching or these files. This patch should fix the issue.

Subject tree based browse views

If a browse view uses a subject field like subjects or divisions the number of items listed under ancestor (e.g. parent) divisions will be wrong. This patch can be applied to fix the issue.

Decimal MetaField

If you add a field (e.g. to your archive's cfg/cfg.d/eprint_fields.pl. Then

Couldn't parse EPrints::MetaField::Decimal: syntax error at /opt/eprints3/bin/../perl_lib/EPrints/MetaField/Decimal.pm line 80, near "->get_max_input_size 

'aria-labelledby'" This is due the a typo in the Decimal MetaField which is not used by default, only if the configuration for a field with type => 'decimal' is defined. This can be simply fixed by add a comma (,) at the end of the following line:

maxlength=>$self->get_max_input_size

Planned Development

See EPrints 3.4.5